Skip to content

Conversation

@zpao
Copy link
Contributor

@zpao zpao commented Mar 26, 2019

This upgrades the pixel to use https, which in turn eliminates the
insecure content warnings on pytorch.org

This upgrades the pixel to use https, which in turn eliminates the
insecure content warnings on pytorch.org
@facebook-netlify-bot
Copy link

Deploy preview for pytorch-dot-org-preview ready!

Built with commit e02660d

https://deploy-preview-177--pytorch-dot-org-preview.netlify.com

@zpao
Copy link
Contributor Author

zpao commented Mar 26, 2019

Note that this doesn't actually update all of the old pages. I think we need to either manually codemod and/or regenerate from sphinx.

@soumith soumith merged commit aba961e into pytorch:site Mar 27, 2019
facebook-github-bot pushed a commit to pytorch/pytorch that referenced this pull request Mar 27, 2019
Summary:
There are a number of pages in the docs that serve insecure content. AFAICT this is the sole source of that.

I wasn't sure if docs get regenerated for old versions as part of the automation, or if those would need to be manually done.

cf. pytorch/pytorch.github.io#177
Pull Request resolved: #18508

Differential Revision: D14645665

Pulled By: zpao

fbshipit-source-id: 003563b06048485d4f539feb1675fc80bab47c1b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants